E2E: Added command and page to interact with app pages #821
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
This PR adds an AppPage that will make it easier to write tests agains pages added within a Grafana app plugin. It removes the need of constructing the base path
/a/${pluginId}
in every test. If we, for some reason, change the base path for apps we have this thin layer where we can cater for that in different versions of Grafana.This functionality can be used in two different ways.
Either you call
gotoAppPage({pluginId: '', path: ''})
to navigate to the page you want to test.Or you can create your own app fixture that you can use within your plugin to write tests.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
📦 Published PR as canary version:
Canary Versions
✨ Test out this PR locally via:
npm install @grafana/create-plugin@4.3.0-canary.821.518e194.0 npm install @grafana/plugin-e2e@0.22.0-canary.821.518e194.0 # or yarn add @grafana/create-plugin@4.3.0-canary.821.518e194.0 yarn add @grafana/plugin-e2e@0.22.0-canary.821.518e194.0